fix(npm): preserve explicit setup versions - #465
Conversation
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 78f39483b6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
morluto
changed the title
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ed000e1459
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
1 participant
Description
npm consumes a positional package spec before launching the selected binary. Once REA starts,
npx rea-agents setupandnpx rea-agents@2.4.0 setupcan therefore expose the same arguments and environment. The dispatcher cannot safely refresh one without risking replacement of an intentional exact-version request.This change removes that ambiguous hidden self-relaunch. Each README keeps one low-friction
npx rea-agents setupfirst-run entrypoint. Repeated quick-start, agent setup, terminal/no-install, and post-install paths explicitly request current online metadata withnpx --yes --prefer-online rea-agents@latest setup. REA always runs the version npm selected.The obsolete bootstrap helper, declaration, package entry, and implementation-shaped tests are removed. Documentation conformance now guards both the simple first-run entrypoint and the explicit freshness/rollback contract.
Intentional rollbacks remain available through:
npm exec --yes --package=rea-agents@2.4.0 -- rea setupType of Change
Testing Performed
npm exec -- vitest run tests/boundary/cli/dispatcher.test.ts tests/conformance/readmeConsistency.test.ts(10 tests passed)npm run check:fastnpm run docs:checknpm pack --dry-run --json(dispatcher present; removed bootstrap absent)npm run verify:packagebuilt and packed successfully, then stopped in the unrelated Linux Hopper platform check because Xvfb is unavailable on the local hostTool Contract Impact
None. MCP tools and schemas are unchanged.